Mobile device for requesting the capture of an image

ABSTRACT

A mobile device for requesting a capture of an image includes a beacon and a processing circuit. The beacon is configured to communicate with an unmanned camera. The processing circuit is configured to generate a request for the unmanned camera to capture an image of a user of the mobile device, where the request includes a condition that must be met by the image of the user, and send the request, via the beacon, to the unmanned camera.

BACKGROUND

Unmanned cameras have become ubiquitous in modern society. For example,cameras are now installed on street lights, buildings, bridges, alongpublic transportation routes, etc. Typically, these unmanned cameras areconfigured for a variety of primary operations, including securitymonitoring, traffic monitoring, and road safety monitoring. Also, thesecameras are often connected to a monitoring center or otherwise linkedto the Internet such that the cameras may communicate with otherdevices.

SUMMARY

One embodiment relates to a mobile device for requesting a capture of animage, the mobile device includes a beacon and a processing circuit. Thebeacon is configured to communicate with an unmanned camera. Theprocessing circuit is configured to generate a request for the unmannedcamera to capture an image of a user of the mobile device, where therequest includes a condition that must be met by the image of the user,and send the request, via the beacon, to the unmanned camera.

Another embodiment relates to a method of requesting a capture of animage. The method includes generating, with a processing circuit, arequest for an unmanned camera to capture an image of a user of a mobiledevice comprising the processing circuit and a beacon, wherein thebeacon is configured to communicate with the unmanned camera, andwherein the request includes a condition that must be met by the imageof the user. The method further includes sending the request, via thebeacon, to the unmanned camera.

Another embodiment relates to a non-transitory computer-readable mediumhaving instructions stored thereon, that when executed by a computingdevice cause the computing device to perform operations for requesting acapture of an image. The operations include generating a request for anunmanned camera to capture an image of a user of a mobile devicecomprising a beacon, wherein the beacon is configured to communicatewith the unmanned camera, and wherein the request includes a conditionthat must be met by the image of the user. The operations furtherinclude sending the request, via the beacon, to the unmanned camera.

Another embodiment relates to a mobile device for requesting a captureof an image, the mobile device includes a beacon and a processingcircuit. The beacon is configured to communicate with an unmannedcamera. The processing circuit is configured to generate a request forthe unmanned camera to capture an image of a user of the mobile device,where the request stipulates a price that the user will pay for theimage, and send the request, via the beacon, to the unmanned camera.

Another embodiment relates to a method of requesting a capture of animage. The method includes generating, with a processing circuit, arequest for an unmanned camera to capture an image of a user of a mobiledevice comprising the processing circuit and a beacon, wherein thebeacon is configured to communicate with the unmanned camera, andwherein the request stipulates a price that the user will pay for theimage. The method further includes sending the request, via the beacon,to the unmanned camera.

Another embodiment relates to a non-transitory computer-readable mediumhaving instructions stored thereon, that when executed by a computingdevice cause the computing device to perform operations for requesting acapture of an image. The operations include generating a request for anunmanned camera to capture an image of a user of a mobile devicecomprising a beacon, wherein the beacon is configured to communicatewith the unmanned camera, and wherein the request stipulates a pricethat the user will pay for the image. The operations further includesending the request, via the beacon, to the unmanned camera.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a mobile device for requesting the captureof an image according to one embodiment.

FIG. 2 is a block diagram of a processing circuit according to oneembodiment.

FIG. 3 is a schematic diagram of a mobile device for requesting thecapture of an image according to one embodiment.

FIG. 4 is a flowchart of a process for requesting the capture of animage according to one embodiment.

FIG. 5 is a flowchart of a process for requesting the capture of animage according to one embodiment.

FIG. 6 is a flowchart of a process for requesting the capture of animage according to one embodiment.

FIG. 7 is a flowchart of a process for requesting the capture of animage according to one embodiment.

FIG. 8 is a flowchart of a process for requesting the capture of animage according to one embodiment.

FIG. 9 is a flowchart of a process for requesting the capture of animage according to one embodiment.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the scope of the subject matter presented here.

Referring generally to the figures, various embodiments of mobiledevices, methods, and computer readable mediums for requesting thecapture of an image are shown and described. In general, unmannedcameras have become commonplace in the present-day world. Particularlyin urban environments cameras are used to automatically monitor roads,traffic, stores, walkways, and public transportation routes (e.g.,elevated trains, subways, buses, etc.). These cameras are usuallyconnected to a network, the Internet, a control center, etc., so thatthey may transmit images/video and be remotely accessed or otherwisecontrolled. The prevalence of unmanned cameras can be harnessed to allowa person to request that a nearby camera to take his or her photographand/or video. A beacon may be used to transmit a request directly to thecamera (or a receiver device connected to the camera). The beacon mayinclude a reflective/fluorescent material, an RFID tag, and othercomponents to transmit/receive a signal (e.g., a light, a radiofrequencytransceiver, an ultrasonic transceiver, sensors, etc.). The request canbe generated by a processing circuit of the beacon or of a devicecoupled to the beacon. In some embodiments the beacon can indirectlytransmit the request to the camera, e.g., it may send the request via acommunications network (e.g., cellular or Wi-Fi network) to a website orelectronic address communicatively coupled to the camera. Thus, based onthe parameters of such a request, the nearby unmanned camera canautomatically capture an image of the person. The request may includevarious conditions, contact information, image specifications, and/orpricing information related to a desired image, as will be discussed infurther detail herein. It should be understood, that although thepresent application often uses the term “image,” the scope of thepresent application is not limited to embodiments for requesting a stillimage (i.e. a photograph). Any of the embodiments disclosed herein allowa user to request a still image, a series of images, and/or a videoclip, from an unmanned camera.

Referring to FIG. 1 a block diagram of mobile device 100 for requestingthe capture of an image is shown. According to one embodiment, mobiledevice 100 is a device that includes beacon 102 and processing circuit104. Such a device may be a laptop, a dedicated beacon device, acellular phone, or any mobile device. Beacon 102 is generally configuredto communicate with an unmanned camera. Beacon 102 may include one ormore transmitters or communication components. In one embodiment, beacon102 includes a light device (e.g., an LED, etc.) configured to generatepulses of light to communicate with the camera. In another embodiment,beacon 102 includes a radiofrequency transmitter configured to transmitan RF signal to communicate with the camera. In another embodiment,beacon 102 includes an ultrasonic transmitter configured to transmit anultrasonic signal to communicate with the camera. Beacon 102 isconfigured to both send and receive data, and is communicably coupled toprocessing circuit 104. Processing circuit 104 interfaces with thecomponents of beacon 102 to transmit a request for the camera to capturean image of the user of the mobile device 100. In one embodiment, beacon102 includes a radiofrequency transceiver (e.g., a Wi-Fi device) of amobile computer, and processing circuit 104 includes the processingcomponents of the mobile computer. In another embodiment, beacon 102includes an LED of a mobile device, and processing circuit 104 includesthe processing components of the mobile device. In another embodiment,beacon 102 includes the cellular transceiver components of a wirelesscommunication device, and processing circuit 104 includes the processingcomponents of the wireless communication device. In another embodiment,beacon 102 and processing circuit 104 are part of a standalonerequesting-device.

Referring to FIG. 2, a block diagram of processing circuit 200 forimplementing at least one embodiment is depicted. Processing circuit 200is generally configured to communicate with a beacon to control theoperation of the beacon. Processing circuit 200 is further configured togenerate a request to be transmitted via the beacon. The request is foran unmanned camera to capture an image of the user. Processing circuit200 may accept input data continuously or periodically. Processingcircuit 200 uses the input data to control a configuration of the beaconand to set properties of the request. Processing circuit 200 generatesvarious conditional data, pricing data, view constraint data, andcontact data to be formatted as part of a request. Any of the datagenerated by processing circuit 200 may be based on user input orconfiguration data. In generating a request to be transmitted by thebeacon, processing circuit 200 may make use of machine learning,artificial intelligence, interactions with databases and database tablelookups, pattern recognition and logging, intelligent control, neuralnetworks, fuzzy logic, etc. Processing circuit 200 further includesinput 202 and output 204. Input 202 is configured to receive a datastream (e.g., a digital or analog stream of data) and configurationinformation. Output 204 is configured to output data for transmission(e.g., a request to be transmitted via the beacon) or for use in aconfiguration process of a device having processing circuit 200 and/or abeacon.

According to one embodiment, processing circuit 200 includes processor206. Processor 206 may be implemented as a general-purpose processor, anapplication specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a digital-signal-processor (DSP), agroup of processing components, or other suitable electronic processingcomponents. Processing circuit 200 also includes memory 208. Memory 208may include one or more devices (e.g., RAM, ROM, Flash Memory, hard diskstorage, etc.) for storing data and/or computer code for facilitatingthe various processes described herein. Memory 208 may be or includenon-transient volatile memory or non-volatile memory. Memory 208 mayinclude database components, object code components, script components,or any other type of information structure for supporting the variousactivities and information structures described herein. Memory 208 maybe communicably connected to processor 206 and provide computer code orinstructions to processor 206 for executing the processes describedherein (e.g., the processes shown in FIGS. 4-9). Memory 208 may includememory buffer 210. Memory buffer 210 may be configured to receive a datastream from a user input and/or beacon through input 202. For example,the data may include input related to characteristics of an imagerequested by the user. As another example, the data may include inputfrom a beacon configured to receive feedback from an unmanned camera.The data received through input 202 may be stored in memory buffer 210until memory buffer 210 is accessed for data by the various modules ofmemory 208. For example, request module 214 can access the data that isstored in memory buffer 210. Any data received through input 202 mayalso be immediately accessed.

Memory 208 further includes configuration data 212. Configuration data212 includes data related to processing circuit 200. For example,configuration data 212 may include information related to interfacingwith other components (e.g., sensors and transmitters of the beacon,etc.). Configuration data 212 may also include the command set needed togenerate a user interface or to communicate with other user interfacecomponents (e.g., a touch screen display, a keyboard, etc.). Based ondata stored in configuration data 212, processing circuit 200 may formatdata for output via output 204, which may include formatting data fortransmission via a beacon, etc. For example, processing circuit 200 maygenerate a request and format the request to be transmitted via a seriesof light pulses. As another example, processing circuit 200 may generatea request and format the request to be transmitted via a radiofrequencysignal or ultrasonic signal, according to a wireless networkingprotocol. Processing circuit 200 may also format data for transmissionaccording to any additional protocols or standards as specified byconfiguration data 212. Configuration data 212 may further includeinformation as to how often input should be accepted from a sensordevice. Configuration data 212 may include default values required toinitiate communication with another device (e.g., a mobile phone, etc.)and with any components of the device having processing circuit 200.Configuration data 212 further includes data to configure communicationbetween the various components of processing circuit 200.

Memory 208 further includes request module 214. Request module 214 isconfigured to receive input related to characteristics of requestedimage, generate a request based on the characteristics, and interfacewith a beacon (e.g., beacon 102). Request module 214 also may accessconfiguration information and other data as provided by processingcircuit 200. Request module 214 generates signals to cause the beacon totransmit a generated request.

In one embodiment, a user desires to have his image captured and usesthe beacon to send a request to an unmanned camera. The request isunsolicited by the unmanned camera, and is generally broadcast from thebeacon. Thus, a single nearby unmanned camera, or multiple nearbyunmanned cameras may detect the request. Request module 214 generatesthe request based on input from the user or configuration data 212, andcontrols operation of the beacon such that the request is transmitted.The request may be transmitted by the beacon and received directly bythe unmanned camera, or the request may be received by a separatereceiver device, which forwards the request to the camera. For example,multiple unmanned cameras in a certain area may be connected to a singlereceiver device that is associated with the multiple unmanned cameras.The receiver device may be nearby the camera, or remotely positionedfrom the cameras, and may transmit a received request to one or morecameras in order to capture an image. In one embodiment, the beaconincludes light generation components, and request module 214 controlsthe components to illuminate the light generation components in acertain pattern. Based on the illumination, an unmanned camera candetect the request (and the user) in a frame that the camera iscapturing. The illumination pattern may be based a defined protocol thatis stored in configuration data 212. In another embodiment, the beaconincludes a radiofrequency transceiver, and request module 214 controlsthe transmitter to send a request signal. The request may be sentaccording to a defined protocol or on a certain frequency that is knownthe cameras. For example, according to one configuration with a certaincamera system, an image request may be transmitted by a 150 MHz signal.In another embodiment, the beacon includes an ultrasonic transceiver,and request module 214 controls the transceiver to send an ultrasoundsignal that includes the request. For example, the request may beencoded in a 19 kHz sound wave. It should be understood that otherfrequencies may also be used, and the scope of the present applicationis not limited to the frequencies discussed above. Based on the data ofthe request, an unmanned camera may locate a user and capture the user'simage as specified by the parameters of the request. An unmanned cameramay locate the user based on the location of the beacon. For example,with a beacon that includes a light, a camera may detect the location ofthe illumination in the frame of the camera and base the location of theuser on the detected illumination. An unmanned camera may also analyzethe request data to locate the user. For example, the request mayinclude GPS coordinates or other identification information such that alocation of the user may be discerned. Additional characteristicsrelated to a request may also be included in by request module 214. Anyof the characteristics discussed herein may be based on user input,stored values, or configuration data 212.

In one embodiment, request module 214 generates a request that includesa condition that must be met by the captured image of the user. In otherwords, the request is for the unmanned camera to capture the user'simage, but only under certain conditions. In this manner, a user cancontrol the situations in which his image is captured, as an unmannedcamera that receives the request can capture the image if the conditionsare met, and the camera may disregard the request if the conditions havenot been met. In one embodiment, request module 214 formats the requestto include a view constraint for the image. For example, the viewconstraint may require the image to be a front/rear view of the user. Asanother example, the view constraint may require the image to be of aright/left profile view of the user. As another example, the viewconstraint may require a full body view, an upper body view, or only afacial view, etc. The view constraint may also specify a certaincomposition setting desired of the captured image. For example, viewconstraint may specify that the composition satisfy a rule of thirdscomposition, a golden ratio, or another photographic composition rule.As another example, the view constraint may specify what portion of theimage the user desires to occupy (e.g., left side of the image, centerof the image, etc.). The specified portion may be precisely defined ormay be defined as an allowable range that is acceptable for the user tooccupy.

In one embodiment, the request includes a condition that specifieswhether certain objects or other people are allowed, not allowed, or arerequired to be in a captured image. For example, the condition mayspecify that only the user is allowed to be in the image. As anotherexample, the condition may specify that other people are allowed in theimage, but the image should not contain any cars. The condition may alsospecify the desired location of certain objects or people. For example,the condition may specify that other people are allowed in the image, aslong as they are in the background, foreground, left/right side of theimage, etc.

In one embodiment, the request includes a condition that specifies animage quality requirement. For example, the condition may specify thatthe user requires a certain resolution. The condition may furtherspecify color settings related to the image. For example, the image maybe requested to be taken in (or converted to) black and white, with awarming filter, a cooling filter, standard color, etc. The condition mayfurther specify lighting requirements (e.g., a brightness or contrastrequired, etc.). The lighting requirements may include a range ofacceptable values.

In one embodiment, the request includes a condition that specifies atiming requirement for the image. For example, the timing requirementmay instruct the camera to capture the image the next time all of theconditions of the request can be satisfied. As another example, thetiming requirement may instruct the camera to capture the image after acertain time period has elapsed (e.g., after 5 seconds, after 30seconds, etc.) and any conditions have been satisfied. The timingrequirement may also specify a range within which the image should becaptured (if possible). For example, the timing requirement may instructthe camera to try and capture the image after 5 seconds have elapsed,but only for a period of 15 seconds total. Thus after 15 seconds haveelapsed, if the image could not be captured because conditions of therequest could not be satisfied, the request would expire. In oneembodiment, the timing requirement specifies whether a still image,multiple still images, or a video clip is required. For example, ifmultiple images are requested, the timing requirement may instruct thecamera to capture 5 images during the next 15 seconds, etc. As anotherexample, the timing requirement that instruct the camera to capture 5images but keep only the top rated image (or images). Various imagerating algorithms may be used to rank a composition or quality of animage. Ratings may be based on the content and composition of the imageincluding facial features, expressions, eye direction, etc. For example,if an image is captured where the user is blinking, it may not be ratedas highly as an image where the user's eyes are open. As anotherexample, if a video clip (rather than a still image) is requested, thetiming requirement may specify a frame rate or length of video cliprequired.

In one embodiment, the request includes contact information for theuser. For example, the request may include the user's name, an IDcode/account number related to the user, an email address of the user,and/or a physical or mailing address of the user. The contactinformation may further include information specifying where to sendcaptured images. For example, the request may instruct the unmannedcamera to route a captured image to the user (e.g., to an email addresslisted in the contact information). As another example, the request mayinstruct an unmanned camera to automatically send a captured image andthe user's contact information to a print shop, so that the image may beprinted and mailed to an address in the contact information. As anotherexample, the request may instruct an unmanned camera to route an imageavailability notification to the user (e.g., to his email address, tohis mobile device via a text/MMS message, etc.) when the image isavailable for review. This notification may provide a preview version ofthe image (e.g., a thumbnail, a lower resolution version, a watermarkedversion, etc.). As another example, the request may instruct an unmannedcamera to automatically send a captured image to a specified digitalmemory location, e.g., a server address, a website, a database, adigital locker, or the like. As another example, the request mayinstruct an unmanned camera to send a captured image directly to thebeacon based on transmission settings (e.g., radiofrequency orultrasonic signal configurations) specified in the contact information.

In one embodiment, the request can stipulate a user's willingness to payfor the images. The request may stipulate a price per image and/or aprice for a set of images. A price may be stipulated based on a qualityor view of the image. For example, the user may specify that he iswilling to pay $5 for a highly rated image, $3 if the image is rated asaverage, and not pay anything if the image is poorly rated. As anotherexample, the user may specify that he is willing to pay $5, but only ifthe camera was able to capture an image with the user centered in theframe. The request may further indicate how many copies of an image orhow many separate views the user desires. A request may also includepayment information (e.g., a full or partial payment required) so thatthe user may be billed. For example, the payment information may includeinformation related to a credit card account, a bank account, or anonline payment processor. In one embodiment, the request includes orfacilitates a full or partial electronic payment (e.g., an electronicfunds transfer) to an account related to the camera. In this manner, theuser can pay for a requested image if the camera is able to capture theimage as requested.

In one embodiment, request module 214 generates a solicited request. Forexample, the beacon may be configured to receive a signal from anunmanned camera (or from a separate transmitter associated with anunmanned camera). In this embodiment, the beacon includes a receiverdevice (e.g., a light sensor, a radiofrequency sensor, an ultrasonicsensor, etc.) that detects a probe signal from a camera. The probesignal may be used to notify request module 214 of the camera'spresence. The probe signal may include additional details related to thecamera, such as the camera's location, image price, or capabilities.Upon detection of the probe signal by request module 214, request module214 may generate an alert for the user to notify the user of thecamera's presence and availability to capture an image. For example,request module 214 may interface with various user interface components(e.g., a speaker, a display, a touch screen, etc.) so that the user maybe provided the alert (e.g. a visual or audio alert). This allows a userto initiate a request if desired after the user is notified of thepresence of an unmanned camera. For example, after receiving anotification that a camera is nearby and available to capture an imageof the user, the user may use a user interface to enter details relatedto an image that the user desires to be captured by the camera. Based onthe input, request module 214 generates the request as described herein,and causes the beacon to transmit the request to the camera.

In one embodiment, request module 214 is configured to rescind arequest. In this embodiment, the beacon is configured to receive aconfirmation signal from an unmanned camera (or from a separatetransmitter associated with an unmanned camera). For example, aftersending an initial request using the beacon, request module 214 mayreceive a signal (via the beacon) from the unmanned camera. The signalmay include a confirmation that the initial request was received, thatthe camera will not comply with the request, or that an image wascaptured based on the request. Request module 214 may generate signalsto use a user interface to notify the user of the confirmation. If forsome reason the user desires to cancel the initial request, the user nolonger wants the initial image, or the user would like to cancel anyadditional pending requests, the user can enter such cancellationinstructions via the user interface. Request module 214 may format thecancellation instructions and transmit them (via the beacon) to thecamera such that the request is rescinded, the captured image isdisregarded, or any additional pending requests are rescinded.

It should be understood that request module 214 may generate a requestthat includes any of the various characteristics and conditionsdescribed herein. For example, a single request may include a viewconstraint, a lighting condition, a timing requirement, contactinformation, and/or payment information, etc. Further, a request canspecify whether a captured image or video should or should not includemetadata related to the image. For example, an image can be captured andinclude metadata related to a location or time of the image. However, ifthe request specifies that metadata is not desired, the image file foran image may be formatted without embedded metadata.

Referring to FIG. 3, a schematic diagram of a mobile device 300 forrequesting the capture of an image is shown according to one embodiment.Mobile device 300 includes beacon 302 and processing circuit 304, whichare depicted as components of a cellular phone. For example, beacon 302may be a radiofrequency transmitter of the mobile device, and processingcircuit 304 may include the processing components (e.g., processor,memory, etc.) of the mobile device. User 306 can use the user interfaceof the mobile device to enter details related to an image that user 306desires to be captured by an unmanned camera. For example, user 306 maydesire an image of user 306 centered in the frame and facing the camera,with nobody else in the frame. User 306 may also specify that he willpay $5 for the image and would like it emailed to his email address, andincludes his credit card information. User 306 enters these detailsusing the user interface (e.g., a keypad or touchscreen of the mobiledevice), and processing circuit 304 generates the request based on thedetails. Processing circuit 304 then causes beacon 302 to transmit therequest according to a known radiofrequency signal. The request includesthe GPS coordinates of user 306. Unmanned camera 308, which is depictedas being mounted to light pole 310, detects the request from beacon 302.If it is possible for camera 308 to capture the image according to theconditions of the request (where user 306 is centered and facing thecamera, and no other person is in the frame), the image is captured andemailed to user 306. The credit card of user 306 may then be charged forthe captured image based on the payment information included in therequest.

Referring to FIG. 4, a flow diagram of a process 400 for requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A request isgenerated for an unmanned camera to capture an image of the user of thedevice having the beacon (402). The beacon may be communicably coupledto a mobile device such as a laptop, a cellular phone, etc.Alternatively the beacon may be integrated into the mobile device. Therequest may be an unsolicited request, sent by the beacon.Alternatively, the request may be in response to a probe signal of theunmanned camera that was detected by the beacon or the mobile device.The request includes a condition that must be met by the image of theuser (404). If the condition can be satisfied, the unmanned camera maycapture the image. The request is sent to the unmanned camera (406). Forexample, the beacon may include a radiofrequency transmitter, anultrasonic transmitter, or a light device, etc., that is configured towirelessly communicate with the unmanned camera or a receiving devicecoupled to the unmanned camera.

Referring to FIG. 5, a flow diagram of a process 500 for requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A request isgenerated for an unmanned camera to capture an image of the user of thedevice having the beacon (502). The request includes a condition thatmust be met by the image of the user (504). The condition may includeone or more conditions required of the captured image (506). Forexample, as discussed in detail above, the condition may include a viewconstraint, an image quality requirement, a composition requirement, ora timing requirement. The request is sent to the unmanned camera (508).If each of the conditions of the request can be satisfied (510), thenthe unmanned camera may proceed to capture an image satisfying thevarious conditions (512). The captured image (or images or video) may bereceived directly via the beacon as specified by the request (514).Alternatively, the captured image may be sent to an email address, orotherwise routed as specified by the request.

Referring to FIG. 6, a flow diagram of a process 600 requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A probe signalis received by the beacon from an unmanned camera (602). For example,the unmanned camera may detect an RFID tag of the beacon and transmit acommunication probe signal based on RFID information, notifying thebeacon of its presence. As another example, the unmanned camera may bebroadcasting a generic probe signal (e.g., on a known frequency orchannel, etc.) that the beacon can detect. In response to a detectedprobe signal, a request is generated for the unmanned camera to capturean image of the user of the beacon (604). The request includes acondition that must be met by the image of the user (606). The requestincludes contact information and specifies where to send a capturedimage (608). The request is transmitted to the unmanned camera (610).

Referring to FIG. 7, a flow diagram of a process 700 for requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A request isgenerated for an unmanned camera to capture an image of the user of thedevice having the beacon (702). The request stipulates a price that theuser will pay for the image (704). The price may include one or morepricing models (706). For example, the price may be specified to be aprice per image captured, a price per set of images captured, a pricebased on the quality or view of the captured image (e.g., how clear itis, how bright it is, how well the image is composed, how much of theuser was captured, etc.). The request includes payment information sothat the user may be billed for the image (708). The request is sent tothe unmanned camera (710).

Referring to FIG. 8, a flow diagram of a process 800 requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A request isgenerated for an unmanned camera to capture an image of the user of thedevice having the beacon (802). The request stipulates a price that theuser will pay for the image (804). The price may include one or morepricing models (806). The request further includes an electronic paymentor initiates a transfer of funds to an account related to the unmannedcamera (808). In this manner, the capture image may be paid forimmediately upon capture of the image by the unmanned camera. Therequest is sent to the unmanned camera (810). Based on the includedelectronic payment, the image is paid for upon capture (812). The beaconmay receive a confirmation from the camera that the image was capturedas desired by the user (814). Based on the confirmation, the user mayrescind any additional request that may be pending, if desired (816).For example, the beacon may be used to send a communication to thecamera to notify the camera to rescind pending requests. As anotherexample, the beacon may be used to send a communication to other camerasreceiving the request to notify them to rescind the request (e.g.,because a first camera already took an image satisfying the request).

Referring to FIG. 9, a flow diagram of a process 900 for requesting thecapture of an image is shown, according to one embodiment. Inalternative embodiments, fewer, additional, and/or different actions maybe performed. Also, the use of a flow diagram is not meant to belimiting with respect to the order of actions performed. A request isgenerated for an unmanned camera to capture an image of the user of thedevice having the beacon (902). The request stipulates a price that theuser will pay for the image (904). The request also specifies a timingrequirement for the image as desired by the user (906). One or moretiming requirements may be specified. For example, the user may desire avideo to be captured by the unmanned camera. In this manner, the timingrequirement may specify a length of a video clip desired. As anotherexample, the timing requirement may specify that the image should betaken immediately, or as soon as any conditions required of the imageare satisfied. As another example, the timing requirement may specifythat the image should be captured after a certain period of time (e.g.,after 30 seconds, after a minute, etc.). As another example, the timingrequirement may specify that the unmanned camera should capture multipleimages (e.g., three images total, one image every 15 seconds for aperiod of a minute, etc.). The request is sent to the unmanned camera tocapture the image or video of the user (910).

The construction and arrangement of the systems and methods as shown inthe various embodiments are illustrative only. Although only a fewembodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the embodimentswithout departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

1. A mobile device for requesting a capture of an image, comprising: abeacon configured to communicate with an unmanned camera; and aprocessing circuit configured to: generate a request for the unmannedcamera to capture an image of a user of the mobile device, wherein therequest includes a condition that must be met by the image of the user;and send the request, via the beacon, to the unmanned camera.
 2. Themobile device of claim 1, wherein the condition includes a viewconstraint for the image.
 3. The mobile device of claim 2, wherein theview constraint requires at least one of a frontal view of the user, aleft profile view of the user, a right profile view of the user, a rearview of the user, a full body view of the user, an upper body view ofthe user, and only a facial view of the user.
 4. The mobile device ofclaim 1, wherein the condition specifies a portion of the image that theuser must occupy.
 5. (canceled)
 6. The mobile device of claim 1, whereinthe condition specifies whether certain objects or other people areallowed in the image in addition to the user.
 7. The mobile device ofclaim 1, wherein the condition specifies a composition requirement ofthe image.
 8. The mobile device of claim 1, wherein the conditionspecifies a quality of the image.
 9. The mobile device of claim 8,wherein the quality includes at least one of a resolution requirement, acolor setting, and a lighting condition. 10.-11. (canceled)
 12. Themobile device of claim 1, wherein the request further includes a timingrequirement for the image.
 13. The mobile device of claim 12, whereinthe timing requirement specifies that the image is part of a video andthat the unmanned camera should record the video. 14.-15. (canceled) 16.The mobile device of claim 12, wherein the timing requirement specifiesthat the image should be taken after a certain time period has elapsed.17. The mobile device of claim 12, wherein the timing requirementspecifies that the image should be taken the next time the condition ismet. 18.-39. (canceled)
 40. The mobile device of claim 1, wherein thebeacon includes a light transmitter, and wherein the beacon isconfigured to transmit light to communicate with the unmanned camera.41. The mobile device of claim 1, wherein the beacon includes aradiofrequency transmitter, and wherein the beacon is configured totransmit a radiofrequency signal to communicate with the unmanned camera42. The mobile device of claim 1, wherein the beacon includes anultrasonic transmitter, and wherein the beacon is configured to transmitan ultrasonic signal to communicate with the unmanned camera 43.-47.(canceled)
 48. The mobile device of claim 1, wherein the beacon includesa receiver, wherein the processing circuit is further configured toreceive a probe signal via the receiver of the beacon, wherein the probesignal is related to the unmanned camera, and wherein the request isgenerated in response to receiving the probe signal.
 49. A method ofrequesting a capture of an image, comprising: generating, with aprocessing circuit, a request for an unmanned camera to capture an imageof a user of a mobile device comprising the processing circuit and abeacon, wherein the beacon is configured to communicate with theunmanned camera, and wherein the request includes a condition that mustbe met by the image of the user; sending the request, via the beacon, tothe unmanned camera.
 50. The method of claim 49, wherein the conditionincludes a view constraint for the image. 51.-80. (canceled)
 81. Themethod of claim 49, further comprising receiving a confirmation from theunmanned camera, via the beacon, wherein the confirmation is related tothe request. 82.-83. (canceled)
 84. The method of claim 81, furthercomprising rescinding the request based on input from the user and thereceived confirmation. 85.-95. (canceled)
 96. The method of claim 49,further comprising receiving a probe signal via a receiver of thebeacon, wherein the probe signal is related to the unmanned camera, andwherein the request is generated in response to receiving the probesignal. 97.-144. (canceled)
 145. A mobile device for requesting acapture of an image, comprising: a beacon configured to communicate withan unmanned camera; and a processing circuit configured to: generate arequest for the unmanned camera to capture an image of a user of themobile device, wherein the request stipulates a price that the user willpay for the image; and send the request, via the beacon, to the unmannedcamera.
 146. The mobile device of claim 145, wherein the price is atleast one of a price per image, for a set of images, based on qualityrating of the image, and based on a view of the image. 147.-149.(canceled)
 150. The mobile device of claim 145, wherein the requestfurther includes payment information related to an account of the user.151. (canceled)
 152. The mobile device of claim 150, wherein the paymentinformation includes an electronic transfer of payment. 153.-154.(canceled)
 155. The mobile device of claim 145, wherein the requestfurther includes contact information for the user, and wherein thecontact information includes at least one of a first name, a last name,an email address, an ID code, and an address.
 156. (canceled)
 157. Themobile device of claim 155, wherein the request specifies that an imageavailability notification should be sent to the email address of thecontact information.
 158. The mobile device of claim 157, wherein theimage availability notification includes a preview version of the image.159.-160. (canceled)
 161. The mobile device of claim 145, wherein therequest includes a condition that must be met by the image of the user.162. The mobile device of claim 161, wherein the condition includesspecified at least one of a view constraint for the image, a portion ofthe image that the user must occupy, whether certain objects or otherpeople are allowed in the image in addition to the user, a compositionrequirement of the image, and a quality of the image. 163.-171.(canceled)
 172. The mobile device of claim 145, wherein the requestfurther includes a timing requirement for the image.
 173. The mobiledevice of claim 172, wherein the timing requirement specifies that theimage is part of a video and that the unmanned camera should record thevideo.
 174. The mobile device of claim 173, wherein the timingrequirement further specifies a frame rate of the video. 175.-177.(canceled)
 178. The mobile device of claim 172, wherein the timingrequirement specifies that multiple images should be taken, and whereinthe request specifies that a best rated image of the multiple imagesshould be selected as the image. 179.-181. (canceled)
 182. The mobiledevice of claim 145, wherein the processing circuit is furtherconfigured to receive a confirmation from the unmanned camera, via thebeacon, wherein the confirmation is related to the request. 183.-184.(canceled)
 185. The mobile device of claim 182, wherein the processingcircuit is further configured to rescind the request based on input fromthe user and the received confirmation. 186.-196. (canceled)
 197. Themobile device of claim 145, wherein the beacon includes a receiver,wherein the processing circuit is further configured to receive a probesignal via the receiver of the beacon, wherein the probe signal isrelated to the unmanned camera, and wherein the request is generated inresponse to receiving the probe signal. 198.-305. (canceled)